Methods, apparatuses and computer program products for providing coordination of device to device communication

ABSTRACT

An apparatus for providing coordination of device to device communication may include a processor. The processor is configured to communicate a request for a resource allocation to a network communication node ( 300 ). The resource allocation is related to resources usable for device to device communication between a first terminal communicating the request and a second terminal. The processor is further configured to receive a resource allocation including an amount and duration of resources to be used for the device to device communication in response to the request ( 310 ), and utilize the resource allocation for device to device communication with the second terminal ( 320 ).

TECHNOLOGICAL FIELD

Embodiments of the present invention relate generally to communicationstechnology and, more particularly, relate to apparatuses, methods andcomputer program products for enabling the coordination of device todevice communication.

BACKGROUND

The modern communications era has brought about a tremendous expansionof wireline and wireless networks. Computer networks, televisionnetworks, and telephony networks are experiencing an unprecedentedtechnological expansion, fueled by consumer demand. Wireless and mobilenetworking technologies have addressed related consumer demands, whileproviding more flexibility and immediacy of information transfer.

Current and future networking technologies continue to facilitate easeof information transfer and convenience to users. In order to provideeasier or faster information transfer and convenience, telecommunicationindustry service providers are developing improvements to existingnetworks. In this regard, wireless communication has become increasinglypopular in recent years due, at least in part, to reductions in size andcost along with improvements in battery life and computing capacity ofmobile electronic devices. As such, mobile electronic devices havebecome more capable, easier to use, and cheaper to obtain. Due to thenow ubiquitous nature of mobile electronic devices, people of all agesand education levels are utilizing mobile terminals to communicate withother individuals or contacts, receive services and/or shareinformation, media and other content.

Communication networks and technologies have been developed and expandedto provide robust support for mobile electronic devices. For example,the Worldwide Interoperability for Microwave Access (WiMAX), is atelecommunications technology aimed at providing wireless data over longdistances in a variety of ways, from point-to-point links to full mobilecellular type access. The evolved universal mobile telecommunicationssystem (UMTS) terrestrial radio access network (E-UTRAN) is alsocurrently being developed. The E-UTRAN, which is also known as Long TermEvolution (LTE) or 3.9G, is aimed at upgrading prior technologies byimproving efficiency, lowering costs, improving services, making use ofnew spectrum opportunities, and providing better integration with otheropen standards. In a typical network configuration mobile userscommunicate with each other via communication links maintained by thenetwork. In this regard, for example, an originating station maytypically communicate data to network devices in order for the networkdevices to relay the data to a target station.

Recently, efforts have been made to provide for device to devicecommunication. More particularly, device to device communication sharingthe same band that a communication network such as a cellular networkuses may be desirable. Several mechanisms for enabling device to devicecommunications in this way have been developed recently. For example,Hiperlan 2, Tetra, WLAN (wireless local area network), WiMAX, andTD-SCDMA (Time Division-Synchronous Code Division Multiple Access) areexamples in which such mechanisms have been employed.

In Hiperlan 2, a mobile terminal or user equipment (UE) associated witha first user may send a resource request (e.g., several orthogonalfrequency division multiplexing (OFDM) symbols=slots) for directcommunication with another UE to a central controller. After receiving aresource grant, the UE of the first user may transmit to the UE of theother user in the granted slots within the direct link phase in a mediaaccess control (MAC) frame. If the UE of the other user wants totransmit to the UE of the first user, the UE of the other user also hasto reserve slots for such communication. In one instance, in anacknowledged mode, the central controller reserves slots for theacknowledgements of the other UE. Hiperlan 2 also enables a UE torequest a fixed slot allocation. However, the allocation is always for asingle UE, so the central controller as well as other UEs in a directmode cannot transmit at the same time. Accordingly, this does not makeefficient use of available radio resources since each UE has to reserveslots for each and every transmission which results in high signalingload. Additionally, using fixed slot allocation the number of directlinks in the subnet is limited and only full OFDM symbols can bereserved, which may create a excessively large usage of system bandwidthof, for example, 100 MHz with 2048 subcarriers (e.g., assuming 1600usable subcarriers and 64QAM modulation this equals to 8 kb for one OFDMsymbol, but for example a TCP/IP acknowledgement packet has only a sizeof 320b).

Tetra enables the reservation of several frequency channels for deviceto device communication. However, the fixed allocation of channels fordevice to device communication reduces the amount of resources availablefor base station to UE communication. WLAN enables a UE to sense acommunication medium and, if the medium is free or available, the UEtransmits. However, the access point (AP) has no direct ability tocontrol the device to device links. A proposal has been made withrespect to WiMAX to reserve a zone (e.g., several full OFDM symbols) fordevice to device communication. However, only full OFDM symbols can bereserved which, as indicated above, may be too much for a typical systembandwidth.

In light of the issues discussed above, it may be desirable to provide amechanism for enabling an improved coordination of device to devicecommunications that may address at least some of the problems described.

BRIEF SUMMARY OF EXEMPLARY EMBODIMENTS

A method, apparatus and computer program product are therefore providedthat may enable coordination of device to device communication.Accordingly, an exemplary embodiment of the present invention may enablethe allocation of time/frequency resources to device to deviceconnections. Thus, for example, a first UE may take a lead role insetting up a device to device link between two UEs, while the otherdevice (e.g., a second UE) is a follower. The first UE (e.g., lead UE)may request device resources from the network and, when such resourcesare allocated, communicate the resources to the other UE. As analternative, the network may communicate the resources to both UEs. Ineither case, embodiments of the present invention may provide that theflexibility of OFDM access (OFDMA) be employed to access and to allocateresources in the time and frequency domain to the UEs. As such, forexample, a limited number of subcarriers and time-slots may be providedfor device to device communications. Accordingly, for example, networkresources may be shared between the device to device communication andAP to UE communication links.

In one exemplary embodiment, a method of providing coordination ofdevice to device communication is provided. The method may includereceiving a request for a resource allocation from a first terminal. Theresource allocation may be related to resources usable for device todevice communication between the first terminal and a second terminal.The method may further include determining a resource allocationincluding an amount and duration of resources to be provided in responseto the request, and communicating the resource allocation to the firstterminal.

In another exemplary embodiment, a computer program product forproviding coordination of device to device communication is provided.The computer program product may include at least one computer-readablestorage medium having computer-executable program code portions storedtherein. The computer-executable program code portions may include afirst program code portion, a second program code portion and a thirdprogram code portion. The first program code portion may be forreceiving a request for a resource allocation from a first terminal. Theresource allocation may be related to resources usable for device todevice communication between the first terminal and a second terminal.The second program code portion may be for determining a resourceallocation including an amount and duration of resources to be providedin response to the request. The third program code portion may be forcommunicating the resource allocation to the first terminal.

In another exemplary embodiment, an apparatus for providing coordinationof device to device communication is provided. The apparatus may includea processor that may be configured to receive a request for a resourceallocation from a first terminal. The resource allocation may be relatedto resources usable for device to device communication between the firstterminal and a second terminal. The processor may be further configuredto determine a resource allocation including an amount and duration ofresources to be provided in response to the request, and communicate theresource allocation to the first terminal.

In another exemplary embodiment, an apparatus for providing coordinationof device to device communication is provided. The apparatus includesmeans for receiving a request for a resource allocation from a firstterminal. The resource allocation may be related to resources usable fordevice to device communication between the first terminal and a secondterminal. The apparatus may further include means for determining aresource allocation including an amount and duration of resources to beprovided in response to the request, and means for communicating theresource allocation to the first terminal.

In one exemplary embodiment, a method of providing coordination ofdevice to device communication is provided. The method may includecommunicating a request for a resource allocation to a networkcommunication node. The resource allocation may be related to resourcesusable for device to device communication between a first terminalcommunicating the request and a second terminal. The method may furtherinclude receiving a resource allocation including an amount and durationof resources to be used for the device to device communication inresponse to the request, and utilizing the resource allocation fordevice to device communication with the second terminal.

In another exemplary embodiment, a computer program product forproviding coordination of device to device communication is provided.The computer program product may include at least one computer-readablestorage medium having computer-executable program code portions storedtherein. The computer-executable program code portions may include afirst program code portion, a second program code portion and a thirdprogram code portion. The first program code portion may be forcommunicating a request for a resource allocation to a networkcommunication node. The resource allocation may be related to resourcesusable for device to device communication between a first terminalcommunicating the request and a second terminal. The second program codeportion may be for receiving a resource allocation including an amountand duration of resources to be used for the device to devicecommunication in response to the request. The third program code portionmay be for utilizing the resource allocation for device to devicecommunication with the second terminal.

In another exemplary embodiment, an apparatus for providing coordinationof device to device communication is provided. The apparatus may includea processor that may be configured to communicate a request for aresource allocation to a network communication node. The resourceallocation may be related to resources usable for device to devicecommunication between a first terminal communicating the request and asecond terminal. The processor may be further configured to receive aresource allocation including an amount and duration of resources to beused for the device to device communication in response to the request,and utilize the resource allocation for device to device communicationwith the second terminal.

In another exemplary embodiment, an apparatus for providing coordinationof device to device communication is provided. The apparatus includesmeans for communicating a request for a resource allocation to a networkcommunication node. The resource allocation may be related to resourcesusable for device to device communication between a first terminalcommunicating the request and a second terminal. The apparatus mayfurther include means for receiving a resource allocation including anamount and duration of resources to be used for the device to devicecommunication in response to the request, and means for utilizing theresource allocation for device to device communication with the secondterminal.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is a schematic block diagram of a mobile terminal according to anexemplary embodiment of the present invention;

FIG. 2 is a schematic block diagram of a wireless communications systemaccording to an exemplary embodiment of the present invention;

FIG. 3 illustrates an example of a system for providing coordination ofdevice to device communication according to an exemplary embodiment ofthe present invention;

FIG. 4 illustrates a block diagram showing an apparatus for providingcoordination of device to device communication according to an exemplaryembodiment of the present invention;

FIG. 5 illustrates a first UE and a second UE that are not associatedwith the same AP establishing device to device communication accordingto an exemplary embodiment of the present invention;

FIG. 6 illustrates a first UE and a second UE that are associated withthe same AP establishing device to device communication according to anexemplary embodiment of the present invention; and

FIG. 7 is a flowchart according to an exemplary method of providingcoordination of device to device communication according to an exemplaryembodiment of the present invention; and

FIG. 8 is a flowchart according to another exemplary method of providingcoordination of device to device communication according to an exemplaryembodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like reference numerals refer to like elementsthroughout.

FIG. 1, one exemplary embodiment of the invention, illustrates a blockdiagram of a mobile terminal 10 that would benefit from embodiments ofthe present invention. It should be understood, however, that a mobiletelephone as illustrated and hereinafter described is merelyillustrative of one type of mobile terminal that would benefit fromembodiments of the present invention and, therefore, should not be takento limit the scope of embodiments of the present invention. Whileseveral embodiments of the mobile terminal 10 may be illustrated andhereinafter described for purposes of example, other types of mobileterminals, such as portable digital assistants (PDAs), pagers, mobiletelevisions, gaming devices, laptop computers, cameras, video recorders,audio/video player, radio, GPS devices, or any combination of theaforementioned, and other types of voice and text communicationssystems, can readily employ embodiments of the present invention.

In addition, while several embodiments of the method of the presentinvention are performed or used by a mobile terminal 10, the method maybe employed by other than a mobile terminal. Moreover, the system andmethod of embodiments of the present invention will be primarilydescribed in conjunction with mobile communications applications. Itshould be understood, however, that the system and method of embodimentsof the present invention can be utilized in conjunction with a varietyof other applications, both in the mobile communications industries andoutside of the mobile communications industries.

The mobile terminal 10 may include an antenna 12 (or multiple antennas)in operable communication with a transmitter 14 and a receiver 16. Themobile terminal 10 may further include an apparatus, such as acontroller 20 or other processing element, that provides signals to andreceives signals from the transmitter 14 and receiver 16, respectively.The signals include signaling information in accordance with the airinterface standard of the applicable cellular system, and also userspeech, received data and/or user generated data. In this regard, themobile terminal 10 is capable of operating with one or more airinterface standards, communication protocols, modulation types, andaccess types. By way of illustration, the mobile terminal 10 is capableof operating in accordance with any of a number of first, second, thirdand/or fourth-generation communication protocols or the like. Forexample, the mobile terminal 10 may be capable of operating inaccordance with second-generation (2G) wireless communication protocolsIS-136 (time division multiple access (TDMA)), GSM (global system formobile communication), and IS-95 (code division multiple access (CDMA)),or with third-generation (3G) wireless communication protocols, such asUniversal Mobile Telecommunications System (UMTS), CDMA2000, widebandCDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), with 3.9Gwireless communication protocol such as E-UTRAN, with fourth-generation(4G) wireless communication protocols or the like. As an alternative (oradditionally), the mobile terminal 10 may be capable of operating inaccordance with non-cellular communication mechanisms. For example, themobile terminal 10 may be capable of communication in a wireless localarea network (WLAN) or other communication networks described below inconnection with FIG. 2.

It is understood that the apparatus, such as the controller 20, mayinclude circuitry desirable for implementing audio and logic functionsof the mobile terminal 10. For example, the controller 20 may becomprised of a digital signal processor device, a microprocessor device,and various analog to digital converters, digital to analog converters,and other support circuits. Control and signal processing functions ofthe mobile terminal 10 are allocated between these devices according totheir respective capabilities. The controller 20 thus may also includethe functionality to convolutionally encode and interleave message anddata prior to modulation and transmission. The controller 20 canadditionally include an internal voice coder, and may include aninternal data modem. Further, the controller 20 may includefunctionality to operate one or more software programs, which may bestored in memory. For example, the controller 20 may be capable ofoperating a connectivity program, such as a conventional Web browser.The connectivity program may then allow the mobile terminal 10 totransmit and receive Web content, such as location-based content and/orother web page content, according to a Wireless Application Protocol(WAP), Hypertext Transfer Protocol (HTTP) and/or the like, for example.

The mobile terminal 10 may also comprise a user interface including anoutput device such as a conventional earphone or speaker 24, a ringer22, a microphone 26, a display 28, and a user input interface, all ofwhich are coupled to the controller 20. The user input interface, whichallows the mobile terminal 10 to receive data, may include any of anumber of devices allowing the mobile terminal 10 to receive data, suchas a keypad 30, a touch display (not shown) or other input device. Inembodiments including the keypad 30, the keypad 30 may include theconventional numeric (0-9) and related keys (#, *), and other hard andsoft keys used for operating the mobile terminal 10. Alternatively, thekeypad 30 may include a conventional QWERTY keypad arrangement. Thekeypad 30 may also include various soft keys with associated functions.In addition, or alternatively, the mobile terminal 10 may include aninterface device such as a joystick or other user input interface. Themobile terminal 10 further includes a battery 34, such as a vibratingbattery pack, for powering various circuits that are required to operatethe mobile terminal 10, as well as optionally providing mechanicalvibration as a detectable output.

The mobile terminal 10 may further include a user identity module (UIM)38. The UIM 38 is typically a memory device having a processor built in.The UIM 38 may include, for example, a subscriber identity module (SIM),a universal integrated circuit card (UICC), a universal subscriberidentity module (USIM), a removable user identity module (R-UIM), etc.The UIM 38 typically stores information elements related to a mobilesubscriber. In addition to the UIM 38, the mobile terminal 10 may beequipped with memory. For example, the mobile terminal 10 may includevolatile memory 40, such as volatile Random Access Memory (RAM)including a cache area for the temporary storage of data. The mobileterminal 10 may also include other non-volatile memory 42, which can beembedded and/or may be removable. The non-volatile memory 42 canadditionally or alternatively comprise an electrically erasableprogrammable read only memory (EEPROM), flash memory or the like, suchas that available from the SanDisk Corporation of Sunnyvale, Calif., orLexar Media Inc. of Fremont, Calif. The memories can store any of anumber of pieces of information, and data, used by the mobile terminal10 to implement the functions of the mobile terminal 10. For example,the memories can include an identifier, such as an international mobileequipment identification (IMEI) code, capable of uniquely identifyingthe mobile terminal 10. Furthermore, the memories may store instructionsfor determining cell id information. Specifically, the memories maystore an application program for execution by the controller 20, whichdetermines an identity of the current cell, i.e., cell id identity orcell id information, with which the mobile terminal 10 is incommunication.

FIG. 2 is a schematic block diagram of a wireless communications systemaccording to an exemplary embodiment of the present invention. Referringnow to FIG. 2, an illustration of one type of system that would benefitfrom embodiments of the present invention is provided. The systemincludes a plurality of network devices. As shown, one or more mobileterminals 10 may each include an antenna 12 for transmitting signals toand for receiving signals from a base site or base station (BS) 44. Thebase station 44 may be a part of one or more cellular or mobile networkseach of which includes elements required to operate the network, such asa mobile switching center (MSC) 46. As well known to those skilled inthe art, the mobile network may also be referred to as a BaseStation/MSC/Interworking function (BMI). In operation, the MSC 46 iscapable of routing calls to and from the mobile terminal 10 when themobile terminal 10 is making and receiving calls. The MSC 46 can alsoprovide a connection to landline trunks when the mobile terminal 10 isinvolved in a call. In addition, the MSC 46 can be capable ofcontrolling the forwarding of messages to and from the mobile terminal10, and can also control the forwarding of messages for the mobileterminal 10 to and from a messaging center. It should be noted thatalthough the MSC 46 is shown in the system of FIG. 2, the MSC 46 ismerely an exemplary network device and embodiments of the presentinvention are not limited to use in a network employing an MSC.

The MSC 46 can be coupled to a data network, such as a local areanetwork (LAN), a metropolitan area network (MAN), and/or a wide areanetwork (WAN). The MSC 46 can be directly coupled to the data network.In one typical embodiment, however, the MSC 46 is coupled to a gatewaydevice (GTW) 48, and the GTW 48 is coupled to a WAN, such as theInternet 50. In turn, devices such as processing elements (e.g.,personal computers, server computers or the like) can be coupled to themobile terminal 10 via the Internet 50. For example, as explained below,the processing elements can include one or more processing elementsassociated with a computing system 52 (two shown in FIG. 2), originserver 54 (one shown in FIG. 2) or the like, as described below.

The BS 44 can also be coupled to a serving GPRS (General Packet RadioService) support node (SGSN) 56. As known to those skilled in the art,the SGSN 56 is typically capable of performing functions similar to theMSC 46 for packet switched services. The SGSN 56, like the MSC 46, canbe coupled to a data network, such as the Internet 50. The SGSN 56 canbe directly coupled to the data network. In a more typical embodiment,however, the SGSN 56 is coupled to a packet-switched core network, suchas a GPRS core network 58. The packet-switched core network is thencoupled to another GTW 48, such as a gateway GPRS support node (GGSN)60, and the GGSN 60 is coupled to the Internet 50. In addition to theGGSN 60, the packet-switched core network can also be coupled to a GTW48. Also, the GGSN 60 can be coupled to a messaging center. In thisregard, the GGSN 60 and the SGSN 56, like the MSC 46, may be capable ofcontrolling the forwarding of messages, such as MMS messages. The GGSN60 and SGSN 56 may also be capable of controlling the forwarding ofmessages for the mobile terminal 10 to and from the messaging center.

In addition, by coupling the SGSN 56 to the GPRS core network 58 and theGGSN 60, devices such as a computing system 52 and/or origin server 54may be coupled to the mobile terminal 10 via the Internet 50, SGSN 56and GGSN 60. In this regard, devices such as the computing system 52and/or origin server 54 may communicate with the mobile terminal 10across the SGSN 56, GPRS core network 58 and the GGSN 60. By directly orindirectly connecting mobile terminals 10 and the other devices (e.g.,computing system 52, origin server 54, etc.) to the Internet 50, themobile terminals 10 may communicate with the other devices and with oneanother, such as according to the Hypertext Transfer Protocol (HTTP)and/or the like, to thereby carry out various functions of the mobileterminals 10.

Although not every element of every possible mobile network is shown anddescribed herein, it should be appreciated that the mobile terminal 10may be coupled to one or more of any of a number of different networksthrough the BS 44. In this regard, the network(s) may be capable ofsupporting communication in accordance with any one or more of a numberof first-generation (1G), second-generation (2G), 2.5G, third-generation(3G), 3.9G, fourth-generation (4G) mobile communication protocols or thelike. For example, one or more of the network(s) can be capable ofsupporting communication in accordance with 2G wireless communicationprotocols IS-136 (TDMA), GSM, and IS-95 (CDMA). Also, for example, oneor more of the network(s) can be capable of supporting communication inaccordance with 2.5G wireless communication protocols GPRS, EnhancedData GSM Environment (EDGE), or the like. Further, for example, one ormore of the network(s) can be capable of supporting communication inaccordance with 3G wireless communication protocols such as a UMTSnetwork employing WCDMA radio access technology. Some narrow-band analogmobile phone service (NAMPS), as well as total access communicationsystem (TACS), network(s) may also benefit from embodiments of thepresent invention, as should dual or higher mode mobile stations (e.g.,digital/analog or TDMA/CDMA/analog phones).

The mobile terminal 10 can further be coupled to one or more wirelessaccess points (APs) 62. The APs 62 may comprise access points configuredto communicate with the mobile terminal 10 in accordance with techniquessuch as, for example, radio frequency (RF), infrared (IrDA) or any of anumber of different wireless networking techniques, including WLANtechniques such as IEEE 802.11 (e.g., 802.11a, 802.11b, 802.11g,802.11n, etc.), world interoperability for microwave access (WiMAX)techniques such as IEEE 802.16, and/or wireless Personal Area Network(WPAN) techniques such as IEEE 802.15, BlueTooth (BT), ultra wideband(UWB) and/or the like. The APs 62 may be coupled to the Internet 50.Like with the MSC 46, the APs 62 can be directly coupled to the Internet50. In one embodiment, however, the APs 62 are indirectly coupled to theInternet 50 via a GTW 48. Furthermore, in one embodiment, the BS 44 maybe considered as another AP 62. As will be appreciated, by directly orindirectly connecting the mobile terminals 10 and the computing system52, the origin server 54, and/or any of a number of other devices, tothe Internet 50, the mobile terminals 10 can communicate with oneanother, the computing system, etc., to thereby carry out variousfunctions of the mobile terminals 10, such as to transmit data, contentor the like to, and/or receive content, data or the like from, thecomputing system 52. As used herein, the terms “data,” “content,”“information” and similar terms may be used interchangeably to refer todata capable of being transmitted, received and/or stored in accordancewith embodiments of the present invention. Thus, use of any such termsshould not be taken to limit the spirit and scope of embodiments of thepresent invention.

Although not shown in FIG. 2, in addition to or in lieu of coupling themobile terminal 10 to computing systems 52 across the Internet 50, themobile terminal 10 and computing system 52 may be coupled to one anotherand communicate in accordance with, for example, RF, BT, IrDA or any ofa number of different wireline or wireless communication techniques,including LAN, WLAN, WiMAX, UWB techniques and/or the like. One or moreof the computing systems 52 can additionally, or alternatively, includea removable memory capable of storing content, which can thereafter betransferred to the mobile terminal 10. Further, the mobile terminal 10can be coupled to one or more electronic devices, such as printers,digital projectors and/or other multimedia capturing, producing and/orstoring devices (e.g., other terminals). Like with the computing systems52, the mobile terminal 10 may be configured to communicate with theportable electronic devices in accordance with techniques such as, forexample, RF, BT, IrDA or any of a number of different wireline orwireless communication techniques, including universal serial bus (USB),LAN, WLAN, WiMAX, UWB techniques and/or the like.

In some embodiments, the mobile terminal 10 may be capable of receivingcommunication from multiple cells (e.g., multiple BSs or APs) at anygiven time or at different times. Furthermore, in some embodiments, thesystem of FIG. 2 could represent a multiple radio access technologyenvironment. In this regard, for example, the BS 44 may be coupled tothe SGSN 56 and the MSC 46 via a base station controller (BSC) 45 thatmay control the BS 44. The BS 44 and the BSC 45 may be associated with afirst radio access technology (RAT) (e.g., a 2G RAT). Meanwhile, theSGSN 56 and the MSC 46 may also be coupled to a radio network controller(RNC) 47 of a second RAT (e.g., a 3G RAT). The RNC 47 may in turn be incommunication with one or more nodes (e.g., node-Bs) 49, one or more ofwhich may be capable of communication with the mobile terminal 10 at anygiven time. As such, the mobile terminal 10 may be configured to be ableto communicate with (e.g., select a cell associated with) either thefirst RAT or the second RAT. Furthermore, additional RATs may also beincluded in the system of FIG. 2 so that the mobile terminal 10 may beenabled to communicate with any of a plurality of different RATs.

In an exemplary embodiment, content or data may be communicated over thesystem of FIG. 2 between a mobile terminal, which may be similar to themobile terminal 10 of FIG. 1, and a network device of the system of FIG.2 in order to, for example, execute applications or establishcommunication (for example, for purposes of content or informationsharing) between the mobile terminal 10 and other mobile terminals. Assuch, it should be understood that the system of FIG. 2 need not beemployed for communication between mobile terminals or between a networkdevice and the mobile terminal, but rather FIG. 2 is merely provided forpurposes of example. Furthermore, it should be understood thatembodiments of the present invention may be resident on a communicationdevice such as the mobile terminal 10, and/or may be resident on aserver, personal computer or other device, absent any communication withthe system of FIG. 2.

An exemplary embodiment of the present invention will now be describedin connection with an LTE system in operation in the same area as twodevices seeking to establish device to device communications. As such,it may be assumed that the two devices may each be capable ofcommunication with LTE system or network devices. However, as indicatedin FIG. 2, embodiments of the present invention could also be employedin connection with other RATs such as, for example, other OFDMA systemssuch as IEEE 802.16 techniques like WiMAX. As such, an exemplaryembodiment of coordination of device to device communication will bedescribed hereinafter in connection with the example shown in FIGS. 3and 4.

Referring now to FIG. 3, a schematic block diagram showing a system forproviding a mechanism for enabling coordination of device to devicecommunication according to an exemplary embodiment of the presentinvention is provided. However, FIG. 3 is illustrative of one exemplaryembodiment, and it should be understood that other architecturesincluding additional or even fewer elements may also be employed inconnection with practicing embodiments of the present invention. Thesystem includes an E-UTRAN 76 which may include, among other things, aplurality of node-Bs in communication with an EPC 78 which may includeone or more mobility management entities (MMES) and one or more systemarchitecture evolution (SAE) gateways. The node-Bs may be E-UTRANnode-Bs (e.g., eNBs 72) and may also be in communication with a first UE70 and a second UE 71. Although FIG. 3 only shows a specific number ofeNBs and UEs, there could be a plurality of nodes and mobile terminalsincluded in the system. The E-UTRAN 76 may be in communication with theEPC 78 as part of an EPS (Evolved Packet System). Moreover, althoughFIG. 3 shows evolved node-Bs as the access points (APs), any AP or BSmay be employed in connection with embodiments that operate inconnection with other RATs.

The eNBs 72 may provide E-UTRA user plane and control plane (radioresource control (RRC)) protocol terminations for the first and secondUEs 70 and 71. The eNBs 72 may provide functionality hosting for suchfunctions as radio resource management, radio bearer control, radioadmission control, connection mobility control, dynamic allocation ofresources to UEs in both uplink and downlink, selection of an MME at UEattachment, IP header compression and encryption, scheduling of pagingand broadcast information, routing of data, measurement and measurementreporting for configuration mobility, and the like.

The MME may host functions such as distribution of messages torespective node-Bs, security control, idle state mobility control, EPSbearer control, ciphering and integrity protection of NAS signaling, andthe like. The SAE gateway may host functions such as termination andswitching of certain packets for paging and support of UE mobility. Inan exemplary embodiment, the EPC 78 may provide connection to a networksuch as the Internet.

As shown in FIG. 3, the first UE 70 may be in communication with thesecond UE 71 via device to device communication that may have beenestablished by any known or available mechanism. Embodiments of thepresent invention may then be used to establish new or change previouscommunication allocations for enabling device to device communicationsvia the same resources that permit device to access point (e.g., BS, AP,NB, eNB, etc.) communication. The first and second UEs 70 and 71 mayeach also be capable of communication with the eNB 72. However, inalternative embodiments, only one of the first and second UEs 70 and 71may actually be associated with the AP (e.g., eNB 72). Moreover, as willbe seen below, embodiments of the present invention may enable theprovision of communications between multiple devices via device todevice communication and between an AP and another device sharing thesame resources. For example, the first and second UEs 70 and 71 mayreceive resource allocations from the eNB 72 with respect to device todevice communications while the eNB 72 may concurrently utilizeresources for communication with a third UE 79.

In an exemplary embodiment, one or more of the nodes or devices (e.g.,the eNB 72, the first UE 70, and the second UE 71) may include anapparatus according to an exemplary embodiment of the present invention.The apparatus, an example of which is described below in the context ofFIG. 4, may enable the respective node or device to operate inaccordance with embodiments of the present invention. In this regard,for example, the apparatus may provide for an ability for one of thefirst and second UEs 70 and 71 (e.g., the first UE 70) to act as a leadUE with respect to coordination of device to device communication asdescribed herein, while the other of the first and second UEs 70 and 71(e.g., the second UE 71) may act as a follower UE. In other exemplaryembodiments, a UE such as the first UE 70 acting as the lead terminalmay request resources for device to device communication with multipleUEs. Furthermore, if one or more of the multiple UEs is associated witha different access point (e.g., different eNBs, nodes, base stations,etc.), multiple UEs, or even each UE, may request their own resourcesfor device to device communication from their respective access points.As another alternative example, a device acting as the follower terminal(e.g., the second UE 71) may also request resources for device to devicecommunication.

In an exemplary embodiment, the first UE may employ one embodiment of adevice to device (D2D) communication coordinator 88 (see FIG. 4), forinitiating D2D communication (e.g., direct communication between thefirst UE and the second UE without signaling from a network device suchas an access point, base station or communication node) with the secondUE, while the second UE may include another embodiment of the D2Dcommunication coordinator 88 for receiving information indicative ofresources allocated for D2D communication with the first UE. In thisregard, since the first UE and second UE are merely role designationsand not necessarily indicative of different capabilities, the D2Dcommunication coordinator 88 employed on each of the first and secondUEs may essentially be identical except that different functionalitiesof the D2D communication coordinator 88 may be utilized in eachrespective role. In another exemplary embodiment, the AP (e.g., eNB 72)may include yet another embodiment of the D2D communication coordinator88 for responding to a request for resources for D2D communication fromthe first UE, which may include the allocation of resources. As shown inFIG. 3, according to an exemplary embodiment, the D2D communicationcoordinator 88 may be embodied as any of a resource allocator 80 (e.g.,when embodied at the AP), a resource requestor 82 (e.g., when embodiedat the first UE), or a resource receiver 84 (e.g., when embodied at thesecond UE).

FIG. 4 shows a block diagram view of one example of an apparatusconfigured to perform exemplary embodiments of the present invention. Inthis regard, for example, an apparatus for enabling coordination of D2Dcommunication according to an exemplary embodiment of the presentinvention may be embodied as or otherwise employed, for example, on themobile terminal 10 (e.g., the first or second UE 70, 71) or the eNB 72.However, it should be noted that the apparatus of FIG. 4, may also beemployed on a variety of other devices, both mobile and fixed, andtherefore, embodiments of the present invention should not necessarilybe limited to application on devices such as mobile terminals or APs. Itshould also be noted that while FIG. 4 illustrates one example of aconfiguration of an apparatus for enabling coordination of D2Dcommunication, numerous other configurations may also be used toimplement embodiments of the present invention.

Referring now to FIG. 4, an apparatus for enabling coordination of D2Dcommunication is provided. The apparatus may include or otherwise be incommunication with a processor 90, a user interface 92, a communicationinterface 94 and a memory device 96. The memory device 96 may include,for example, volatile and/or non-volatile memory (e.g., volatile memory40 and/or non-volatile memory 42 or a memory of or accessible to the eNB72). The memory device 96 may be configured to store information, data,applications, instructions or the like for enabling the apparatus tocarry out various functions in accordance with exemplary embodiments ofthe present invention. For example, the memory device 96 could beconfigured to buffer input data for processing by the processor 90.Additionally or alternatively, the memory device 96 could be configuredto store instructions corresponding to an application for execution bythe processor 90. As yet another alternative, the memory device 96 maybe one of a plurality of databases that store information in the form ofstatic and/or dynamic information.

The processor 90 may be embodied in a number of different ways. Forexample, the processor 90 may be embodied as a processing element, acoprocessor, a controller or various other processing means or devicesincluding integrated circuits such as, for example, an ASIC (applicationspecific integrated circuit) or FPGA (field programmable gate array). Inan exemplary embodiment, the processor 90 may be configured to executeinstructions stored in the memory device 96 or otherwise accessible tothe processor 90. Meanwhile, the communication interface 94 may beembodied as any device or means embodied in either hardware, software,or a combination of hardware and software that is configured to receiveand/or transmit data from/to a network and/or any other device or modulein communication with the apparatus. In this regard, the communicationinterface 94 may include, for example, an antenna (or antennas) andsupporting hardware and/or software for enabling communications with awireless communication network.

The user interface 92 may be in communication with the processor 90 toreceive an indication of a user input at the user interface 92 and/or toprovide an audible, visual, mechanical or other output to the user. Assuch, the user interface 92 may include, for example, a keyboard, amouse, a joystick, a trackball, a touch screen display, a conventionaldisplay, a microphone, a speaker, or other input/output mechanisms. Inan embodiment in which the apparatus is embodied at a server or networknode (e.g. the eNB 72), the user interface 92 may be limited or eveneliminated.

As indicated above, in an exemplary embodiment, the apparatus may alsoinclude the D2D communication coordinator 88. The D2D communicationcoordinator 88 may be any means such as a device or circuitry embodiedin hardware, software or a combination of hardware and software that isconfigured to communicate (e.g., via the processor 90) with thecommunication interface 94 in order to transmit and/or receiveinformation related to coordinating D2D communication in accordance withembodiments of the present invention. In some cases the D2Dcommunication coordinator 88 may be further configured to determineresource allocations based on current conditions, user requests, orother factors. In this regard, for example, the D2D communicationcoordinator 88 may be configured to request a resource allocation forD2D communication (e.g., when embodied as the resource requestor 82) andreceive indications or information indicative of the resources allocated(e.g., when embodied as the resource requestor 82 or the resourcereceiver 84). The D2D communication coordinator 88 may alternatively oradditionally be configured to determine and/or provide a resourceallocation for D2D communication to other devices (e.g., when embodiedas the resource requestor 82 or the resource allocator 80) or providechanges or updates to previously provided resource allocationinformation (e.g., when embodied as the resource allocator 80). As such,each of the resource allocator 80, the resource requestor 82, and theresource receiver 84 may be any means such as a device or circuitryembodied in hardware, software or a combination of hardware and softwarethat is configured to perform the corresponding functions of theresource allocator 80, the resource requestor 82, and the resourcereceiver 84, respectively, as described herein.

According to alternative exemplary embodiments, a UE acting as the leadUE (e.g., the first UE 70) may request initiation of resource allocationfor D2D communication from the AP (e.g., a BS, AP, NB, or eNB such aseNB 72), and the resources allocated by the AP may be communicatedeither to both the first UE and another UE acting as the follower UE(e.g., the second UE 71) by the AP or the AP may only provideinformation indicative of the resource allocation to the first UE andthe first UE may provide the information to the second UE. In thisregard, for example, if both the first and second UEs are associatedwith the AP, the AP may provide the information to both the first andsecond UEs. Alternatively, for example, if the second UE is notassociated with the AP, the AP may provide the information to the firstUE and the first UE may pass the information along to the second UEusing an existing connection or a prior resource allocation.

In general, the first UE may operate (e.g., via the resource requestor82) to initiate or schedule direct link communication with the secondUE. According to embodiments of the present invention, the first UErequests resources for such connection from the AP. As such, the AP maygrant resources to the first and second UE (directly or indirectly) inorder to support the communication requested. Meanwhile, the AP mayremain responsible for typical AP functionalities such as paging devicesin D2D communication or communicating with other UEs (e.g., the third UE79) while supporting D2D communication. In an exemplary embodiment, thefirst UE may signal scheduling decisions or other information indicativeof the resource allocation received from the AP to the second UE at aparticular or fixed position within the resources of the AP using, forexample, a D2D common control channel (CCCH). The resources allocated toD2D communication may be those of at least one of the uplink or downlinkphase of the cellular AP to UE communication. D2D communication may thusallocate dedicated uplink resources of cellular communication, dedicateddownlink resources of cellular communication or both uplink and downlinkresources of cellular communication. In a time divided uplink-downlinkcellular duplex, even with a dynamic uplink-downlink switching point,D2D communication may allocate resources specifically from the uplinkshare or specifically from the downlink share, or from both of theuplink and downlink shares of cellular communication in a dynamicmanner. In an exemplary embodiment, specific criteria may exist definingfor D2D communication, which D2D connections utilize resources allocatedfrom the uplink share, which D2D connections utilize resources from thedownlink share, and which connections utilize resources from both thedownlink and uplink shares to thereby give the AP control over optionsfor providing resources for D2D communication. The allocation for D2Dcommunication may actually reuse time-frequency resources for cellularcommunication. Additionally, it may be feasible to dedicate some(temporarily) non-used cellular resources for D2D communication.Moreover, in an exemplary embodiment, the AP (e.g., via the resourceallocator 80) may be configured to make alterations to the resourceallocations previously provided at any time. Such alternations may bemade for a number of reasons such as, for example, in consideration ofor to balance loading, in consideration of or to reduce interference, orother like considerations.

FIG. 5 illustrates one exemplary embodiment in which the first UE (e.g.,UE1 acting as a lead UE) and the second UE (e.g., UE2 acting as afollower UE) are not associated with the same AP (e.g., BS). In thisregard, as shown in FIG. 5, the first UE may request resources from theAP at operation 100. The first UE may then receive a resource grantmessage from the AP at operation 110 and communicate the informationindicative of the resource allocation provided by the resource grant tothe second UE at operation 120. In an exemplary embodiment, when thefirst UE requests resources for a direct link D2D communication with thesecond UE, the AP may allocate resources to be used for the direct linkcommunication at operation 110 (e.g., via the resource allocator 80).The first UE may then inform the second UE of the resource change (e.g.,either from zero resources to some amount of new resources or from someold amount of resources to some new amount of resources). If a commoncontrol channel position changes (e.g., if a particular portion of apredefined bandwidth allotment was initially allocated such as the first20 MHz of a 100 MHz bandwidth and the portion is to be changed later tothe second 20 MHz portion of the bandwidth allotment) a resource changemay be provided by the AP and the first UE may communicate the changevia an old resource allocation. If the common control channel positiondoes not change, a new resource allocation may be used immediately. Inan exemplary embodiment, the AP may provide the resource grant atoperation 110 with, for example, an indication of an expiration for thecorresponding allocation. Thus, for example, a resource allocation maybe valid until either a new resource grant is issued to supersede aprior allocation or the resource allocation expires.

FIG. 6 illustrates an exemplary embodiment in which the first UE (e.g.,UE1) and second UE (e.g., UE2) are both associated with the same AP(e.g., BS). In this example, the first UE may request resources from theAP at operation 150. The first UE may then receive a resource grant fromthe AP at operation 160. Meanwhile, the second UE may also receive theresource grant from the AP at operation 170.

In an exemplary embodiment, a resource request as provided by the firstUE in operations 100 and 150 (e.g., via the resource requester 82) maycontain an indication of the number of resource blocks (RBs) that thefirst UE is requesting for the D2D communication link. In some cases,the first UE may also specify a requested duration for the resourceallocation requested. The duration may be based on a decision made bythe user and a corresponding user input, based on user preferences, auser profile, or may be a predetermined value. An example of a resourcerequest message is provided below in Table 1.

TABLE 1 Example resource request message. Amount of Duration ofresources requested requested allocation Message ID (number of RB)(number of frames) 12 15

In an exemplary embodiment, the AP may grant resources to the UEs forthe D2D link, for example, by allocating adjacent RBs to the direct linkas provided below in Table 2.

TABLE 2 Example resource grant message for adjacent RBs granted todirect link. Amount of First granted RB granted Start of (assumingresources allocation Duration Message numbered RBs (number (in x of IDin a frame) of RB) frames) allocation 5 12 5 15

As an alternative, the AP may signal specific RBs that are granted tothe UEs for the D2D link, for example, in a bitmap as shown in Table 3below.

TABLE 3 Resource grant message using a bitmap to indicate allocation.Message Start of allocation Duration of ID Bitmap (in x frames)allocation 1 0 0 1 0 0 1 0 1 0 1 1 1 5 15 1 1 1 1 0 0 0 0 1 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

As shown in Tables 2 and 3, the AP can further indicate the duration ofthe allocation, the amount of resources granted and when the allocationbegins. The amount of resources granted may be the same as the amountrequested if the AP (e.g., via the resource allocator 80) determinesthat the allocation requested can be supported based on current networkconditions. Alternatively, the amount of resources granted may bedetermined based on current loading, interference or other conditions,or based on a predetermined value.

In situations in which resource allocations are changed, a resourcechange message may be communicated (e.g., either directly to both of theUEs or to the first UE for relaying to the second UE) by the AP. As anexample, if a resource change is conducted due to a change of positionof the common control channel, the resource change message may includeallocated RBs and the position of the common control channel. Tables 4and 5 below provide examples of resource change messages in whichsequentially located RBs are granted (e.g., Table 4) and in which abitmap indicates for which RBs the common control channel has changed(e.g., Table 5).

TABLE 4 Example resource change message for adjacent RBs granted todirect link. RB number 10 will contain the location of the CCCH whereUE1 sends control information (e.g. scheduling information) to UE2.First granted RB Amount of granted Message (assuming numbered resources(number of Location of ID RBs in a frame) RB) CCCH 5 12 10

TABLE 5 Example resource change message using a bitmap to indicateallocation. RB number 11 will contain the location of the CCCH where UE1sends control information (e.g. scheduling information) to UE2. Locationof Message ID Bitmap CCCH 1 0 0 1 0 0 1 0 1 0 1 1 1 1 1 1 11 1 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Embodiments of the present invention may be practiced in connection witha number of different employment options. For example, the commoncontrol channel could be at a fixed position such as the first RB inuse. In some embodiments, system bandwidth may be divided into subbands(e.g., a 20 MHz subband within a 100 MHz bandwidth) and resourceallocation may include an identification of a number corresponding tothe subband allocated in addition to the allocated RBs. In an exemplaryembodiment, the AP may wait until an acknowledgement is received fromthe first UE (and second UE when the second UE is also connected to theAP) before the resource allocation becomes valid. Similarly, aftersending a resource change message to the second UE, the first UE maywait for acknowledgment from the second UE before the assignment isvalid. In some cases, the AP and/or the first UE may not require anacknowledgement from the second UE after a resource grant, but may usehybrid automatic repeat-request (HARQ) or automatic repeat-request (ARQ)to ensure that the resource grant was received. In another exemplaryembodiment, instead of granting resources to a direct link connection,the AP may grant separate resources to the first UE and second UE.

Embodiments of the present invention may provide an AP with full controlover the resources used by D2D links. As such, resources can be flexiblyassigned based on actual traffic conditions with finer granularity thantraditional mechanisms, while maintaining a lower signaling overheadthan some such traditional mechanisms. Embodiments of the presentinvention may also enable the D2D communication links to use the sameresources the AP uses simultaneously (e.g., while the AP uses theresources for communication with other devices). Moreover, the D2D linksprovided by embodiments of the present invention may not reduce theresources used by the AP if the D2D links are not present or in use. Inother words, unlike Tetra, which reserves channels for direct links evenif the links are not in use, embodiments of the present invention mayonly provide the links for a limited duration corresponding to the timethat such links are actually used.

The above described embodiments could also be modified to supportcharging for services provided. For example, the network may grant atoken for a particular data amount or amount or resource consumption.The token could be periodically renewed by the network and the user maybe charged for issuance and renewal of the token. In other alternativeembodiments, the network (e.g., via the AP) may not grant specificresources to UEs for D2D communication. Instead, the network may setaside a portion or plurality of resources into, for example, a resourcepool with indications of (discrete) operation constraints for eachresource in the resource pool. Resources within the pool may then bedynamically shared between multiple D2D connections and allocated by aD2D scheduling entity via, for example, direct signaling or sensingreserved busy bursts. In an exemplary embodiment, busy bursts may beindicative of the reservation of time-frequency resources for D2Dcommunication from the pool of resources. Sensing busy bursts may allowa device to detect in-use or interfered with resources. The device forD2D communication may dynamically select feasible resources for D2Dcommunication and may signal its reservation in busy bursts for theinformation of other devices in that area (e.g., inside the busy burstsignaling range).

FIGS. 7 and 8 are flowcharts of a system, method and program productaccording to exemplary embodiments of the invention. It will beunderstood that each block or step of the flowcharts, and combinationsof blocks in the flowcharts, can be implemented by various means, suchas hardware, firmware, and/or software including one or more computerprogram instructions. For example, one or more of the proceduresdescribed above may be embodied by computer program instructions. Inthis regard, the computer program instructions which embody theprocedures described above may be stored by a memory device of a mobileterminal or node and executed by a processor in the mobile terminal ornode. As will be appreciated, any such computer program instructions maybe loaded onto a computer or other programmable apparatus (i.e.,hardware) to produce a machine, such that the instructions which executeon the computer or other programmable apparatus create means forimplementing the functions specified in the flowcharts block(s) orstep(s). These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable apparatus to function in a particular manner, such that theinstructions stored in the computer-readable memory produce an articleof manufacture including instruction means which implement the functionspecified in the flowcharts block(s) or step(s). The computer programinstructions may also be loaded onto a computer or other programmableapparatus to cause a series of operational steps to be performed on thecomputer or other programmable apparatus to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus provide steps forimplementing the functions specified in the flowcharts block(s) orstep(s).

Accordingly, blocks or steps of the flowcharts support combinations ofmeans for performing the specified functions, combinations of steps forperforming the specified functions and program instruction means forperforming the specified functions. It will also be understood that oneor more blocks or steps of the flowcharts, and combinations of blocks orsteps in the flowcharts, can be implemented by special purposehardware-based computer systems which perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

In this regard, one embodiment of a method for providing coordination ofdevice to device communication from the perspective of a network node asprovided in FIG. 7 may include receiving a request for a resourceallocation from a first terminal (e.g., a lead UE or lead terminal) atoperation 200. The resource allocation may be related to resourcesusable for device to device communication between the first terminal anda second terminal (e.g., a follower terminal). The method may furtherinclude determining a resource allocation including an amount andduration of resources to be provided in response to the request atoperation 210, and communicating the resource allocation to the firstterminal at operation 220.

In an alternative exemplary embodiment, further optional operations maybe included, an example of which is shown in dashed lines in FIG. 7. Inthis regard, the method may further include communicating the resourceallocation to the second terminal at operation 230. In an exemplaryembodiment, communicating the resource allocation may include indicatinga plurality of sequential resource blocks allocated and indicating astarting point of the blocks allocated and a number of frames duringwhich the blocks are to be allocated. Alternatively, communicating theresource allocation may include indicating a plurality of non sequentialresource blocks allocated using a bitmap. In some embodiments,determining the resource allocation may include determining a portion oftime and frequency domain resources used by a network communication nodereceiving the request to be allocated to the first terminal.

In an exemplary embodiment, operation 210 may include determining a poolof available resources with operational constraints for each resource inthe pool and operation 220 may include communicating an identificationof the pool to the first terminal. In such an embodiment, the method mayfurther include enabling utilization of free resources from the pool fordevice to device communication including a third terminal.

In an exemplary embodiment, an apparatus for performing the method abovemay include a processor (e.g., the processor 90) configured to performeach of the operations (200-230) described above. The processor may, forexample, be configured to perform the operations by executing storedinstructions or an algorithm for performing each of the operations.Alternatively, the apparatus may include means for performing each ofthe operations described above. In this regard, according to anexemplary embodiment, examples of means for performing operations 200 to230 may include, for example, an algorithm for managing resourceallocation determination and communications regarding resourceallocations, the D2D communication coordinator 88, the resourceallocator 80, or the processor 90.

Another embodiment of a method for providing coordination of device todevice communication from the perspective of a network node as providedin FIG. 8 may include communicating a request for a resource allocationto a network communication node at operation 300. The resourceallocation may be related to resources usable for device to devicecommunication between a first terminal (e.g., a lead terminal)communicating the request and a second terminal (e.g., a followerterminal). The method may further include receiving a resourceallocation including an amount and duration of resources to be used forthe device to device communication in response to the request atoperation 310 and utilizing the resource allocation for device to devicecommunication with the second terminal at operation 320.

In an alternative exemplary embodiment, further optional operations maybe included, an example of which is shown in dashed lines in FIG. 8. Inthis regard, the method may further include communicating the resourceallocation to the second terminal at operation 315. In an exemplaryembodiment, receiving the resource allocation may include receiving anindication of a plurality of sequential resource blocks allocated andreceiving an indication of a starting point of the blocks allocated anda number of frames during which the blocks are to be allocated.Alternatively, receiving the resource allocation may include receivingan indication of a plurality of non sequential resource blocks allocatedusing a bitmap. In some embodiments, receiving the resource allocationmay include receiving a portion of time and frequency domain resourcesused by the network communication node to be allocated to the firstterminal.

In an exemplary embodiment, operation 310 may include receiving anindication of a pool of available resources with operational constraintsfor each resource in the pool. In such an embodiment, operation 320 mayinclude selecting a portion of the resources in the pool for D2Dcommunication with the second terminal or utilizing the resources of thepool for D2D communication with a third terminal.

In an exemplary embodiment, an apparatus for performing the method abovemay include a processor (e.g., the processor 90) configured to performeach of the operations (300-320) described above. The processor may, forexample, be configured to perform the operations by executing storedinstructions or an algorithm for performing each of the operations.Alternatively, the apparatus may include means for performing each ofthe operations described above. In this regard, according to anexemplary embodiment, examples of means for performing operations 300 to320 may include, for example, an algorithm for managing resourceallocation requests and communications regarding resource allocations,the D2D communication coordinator 88, the resource requester 82, or theprocessor 90.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe exemplary embodiments in the context of certainexemplary combinations of elements and/or functions, it should beappreciated that different combinations of elements and/or functions maybe provided by alternative embodiments without departing from the scopeof the appended claims. In this regard, for example, differentcombinations of elements and/or functions than those explicitlydescribed above are also contemplated as may be set forth in some of theappended claims. Although specific terms are employed herein, they areused in a generic and descriptive sense only and not for purposes oflimitation.

1-37. (canceled)
 38. A method comprising: receiving a request for aresource allocation from a first terminal, the resource allocation beingrelated to resources usable for device to device communication betweenthe first terminal and a second terminal; determining a resourceallocation including an amount and duration of resources to be providedin response to the request; and communicating the resource allocation tothe first terminal.
 39. The method of claim 38, further comprisingcommunicating the resource allocation to the second terminal.
 40. Themethod of claim 38, wherein communicating the resource allocationcomprises indicating a plurality of sequential resource blocks allocatedand indicating a starting point of the blocks allocated and a number offrames during which the blocks are to be allocated.
 41. The method ofclaim 38, wherein communicating the resource allocation comprisesindicating a plurality of non sequential resource blocks allocated usinga bitmap.
 42. The method of claim 38, wherein determining the resourceallocation comprises determining a portion of time and frequency domainresources used by a network communication node receiving the request tobe allocated to the first terminal.
 43. The method of claim 38, whereindetermining the resource allocation comprises determining a pool ofavailable resources with operational constraints for each resource inthe pool and wherein communicating the resource allocation comprisescommunicating an identification of the pool to the first terminal. 44.The method of claim 43, further comprising enabling utilization of freeresources from the pool for device to device communication including athird terminal.
 45. An apparatus comprising a processor; memoryincluding computer program code; the memory and the computer programcode configured to, working with the processor, cause the apparatus toperform at least the following: receive a request for a resourceallocation from a first terminal, the resource allocation being relatedto resources usable for device to device communication between the firstterminal and a second terminal; determine a resource allocationincluding an amount and duration of resources to be provided in responseto the request; and communicate the resource allocation to the firstterminal.
 46. The apparatus of claim 45, wherein the apparatus isfurther configured to communicate the resource allocation to the secondterminal.
 47. The apparatus of claim 45, wherein the processor isconfigured to communicate the resource allocation including anindication of a plurality of sequential resource blocks allocated and anindication of a starting point of the blocks allocated and a number offrames during which the blocks are to be allocated.
 48. The apparatus ofclaim 45, wherein the processor is configured to communicate theresource allocation including an indication of a plurality of nonsequential resource blocks allocated using a bitmap.
 49. The apparatusof claim 45, wherein the processor is configured to determine theresource allocation by determining a portion of time and frequencydomain resources used by a network communication node receiving therequest to be allocated to the first terminal.
 50. An apparatuscomprising a processor; memory including computer program code; thememory and the computer program code configured to, working with theprocessor, cause the apparatus to perform at least the following:communicate a request for a resource allocation to a networkcommunication node, the resource allocation being related to resourcesusable for device to device communication between a first terminalcommunicating the request and a second terminal; receive a resourceallocation including an amount and duration of resources to be used forthe device to device communication in response to the request; andutilize the resource allocation for device to device communication withthe second terminal.
 51. The apparatus of claim 50, wherein theapparatus is further configured to communicate the resource allocationto the second terminal.
 52. The apparatus of claim 50, wherein theprocessor is configured to receive the resource allocation including anindication of a plurality of sequential resource blocks allocated and anindication of a starting point of the blocks allocated and a number offrames during which the blocks are to be allocated.
 53. The apparatus ofclaim 50, wherein the processor is configured to receive the resourceallocation including an indication of a plurality of non sequentialresource blocks allocated using a bitmap.
 54. The apparatus of claim 50,wherein the processor is configured to receive the resource allocationby determining a portion of time and frequency domain resources used bythe network communication node to be allocated to the first terminal.55. The apparatus of claim 50, wherein the processor is configured toreceive the resource allocation comprises receiving an indication of apool of available resources with operational constraints for eachresource in the pool.
 56. The apparatus of claim 55, wherein theprocessor is configured to utilize the resource allocation comprisesutilizing free resources from the pool for device to devicecommunication with a third terminal.
 57. The apparatus of claim 55,wherein the processor is configured to utilize the resource allocationcomprises selecting a portion of the resources in the pool and utilizingthe selected portion for device to device communication with the secondterminal.